-
Couldn't load subscription status.
- Fork 25.6k
Simplify tests, bypassing raw score test #125877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify tests, bypassing raw score test #125877
Conversation
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😞
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
I was debating on having this tests in the original PR anyways. It ain't worth the flakiness. We know the oversampling setting gets updated given the other tests. closes: elastic#125851 (cherry picked from commit 505f21b) # Conflicts: # muted-tests.yml # rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search.vectors/41_knn_search_bbq_hnsw.yml
I was debating on having this tests in the original PR anyways. It ain't worth the flakiness. We know the oversampling setting gets updated given the other tests. closes: #125851 (cherry picked from commit 505f21b) # Conflicts: # muted-tests.yml # rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search.vectors/41_knn_search_bbq_hnsw.yml Co-authored-by: Benjamin Trent <[email protected]>
I was debating on having this tests in the original PR anyways. It ain't worth the flakiness. We know the oversampling setting gets updated given the other tests.
closes: #125851